chore(ci): restore nucleus downstream testing#5497
Merged
Conversation
we don't need it for releases, but still need it for downstream testing
hopefully
rax-it
approved these changes
Sep 17, 2025
Contributor
rax-it
left a comment
rax-it
left a comment
There was a problem hiding this comment.
Approving it as stopgap until we have a path forward with SFCI.
Contributor
Author
|
/nucleus ignore |
Contributor
❌ Error Parsing CommandMissing required argument: reason |
Contributor
Author
|
/nucleus ignore --reason meh |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Details
The
.nucleus.yamlfile was removed in #5464 after we moved publishing fron Nucleus to GitHub Actions. We still need Nucleus for downstream testing, though, so this PR restores the file so we hopefully have the correct configuration. (I'm not 100% sure this is right, the docs aren't super clear.)If you care about the diff, the first commit in this PR restores the file, then changes are made in subsequent commits.
Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item